-
Couldn't load subscription status.
- Fork 2.7k
Accessing each build script's OUT_DIR
#15891
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
75ff71c to
0d5b7b0
Compare
c0d23d2 to
6c8bc08
Compare
5581004 to
c9e3081
Compare
65b6c7f to
4117277
Compare
16fb171 to
8f929ff
Compare
1ab5374 to
b5150ef
Compare
|
r? @weihanglo rustbot has assigned @weihanglo. Use |
|
r? @epage |
OUT_DIROUT_DIR
b5150ef to
3df2913
Compare
3df2913 to
4d74451
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Update cargo submodule 3 commits in 2394ea6cea8b26d717aa67eb1663a2dbf2d26078..801d9b4981dd07e3aecdca1ab86834c13615737e 2025-10-03 14:13:01 +0000 to 2025-10-04 13:30:15 +0000 - chore: Disabled `reserved_windows_name` test temporaily (rust-lang/cargo#16048) - Add panic=immediate-abort support to Cargo (rust-lang/cargo#16041) - Accessing each build script's `OUT_DIR` (rust-lang/cargo#15891)
This PR is continuation of my work on GSoC Project : Build Script Delegation
What does this PR try to resolve?
Through this PR, I want the user to be able to access each build script's
OUT_DIR.How to test and review this PR?
There is a feature gate
multiple-build-scriptsthat can be passed viacargo-featuresinCargo.toml. So, you have to addPreferably on the top of the
Cargo.tomland use nightly toolchain to use the featureThen, you can access the
OUT_DIRof given build script by accessing it like a compile time environment variable, for example: